Search results for "Service-oriented modeling"
showing 3 items of 3 documents
Modeling Requirements for Future CASE
1995
In this paper we discuss some requirements for future CASE Computer Aided Software/Systems Engineering environments. These requirements include increased modifiability and flexibility as well as support for process and agent models. We claim that they can only be addressed by developing more powerful representation and modeling techniques. As a possible basis for modeling various techniques, we outline a general information architecture for a future CASE environment. In addition, we propose primitive types for specifying techniques, the development process, and agent models, and use these types for modeling an example methodology and examine how the requirements are or can be supported in o…
MonPaaS: An Adaptive Monitoring Platformas a Service for Cloud Computing Infrastructures and Services
2015
This paper presents a novel monitoring architecture addressed to the cloud provider and the cloud consumers. This architecture offers a monitoring platform-as-a-Service to each cloud consumer that allows to customize the monitoring metrics. The cloud provider sees a complete overview of the infrastructure whereas the cloud consumer sees automatically her cloud resources and can define other resources or services to be monitored. This is accomplished by means of an adaptive distributed monitoring architecture automatically deployed in the cloud infrastructure. This architecture has been implemented and released under GPL license to the community as “MonPaaS”, open source software for integra…
Systemic Management of Architectural Decisions in Enterprise Architecture Planning. Four Dimensions and Three Abstraction Levels
2006
This paper presents a process model for the management of architectural decisions in enterprise architecture planning. First, decisions are made at the enterprise level, with strategic business considerations on the enterprise information, systems and technology strategy and governance issues. The next step is to define the domains, to then go on with domain architecture decisions. At the systems level, the enterprise and domain architecture decisions are collected and converted into architecture descriptions accurate in precision, form and detail to be given as input to the information systems development process, following the architectural planning. The model is derived from previous wor…